feat: add raw image to allow flexible resolvers #799
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sorry, but this is not how raster data is intended to be used. #772 would require much more work than that. |
|
I'm happy to refactor and follow whatever approach you have in mind |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a RawImage image kind to usvg and a transparent decode_raster implementation in resvg. This allows writing flexible ImageHrefResolver that can support additional image formats. Another use case would be to allow alternate implementations, but with zunejpeg merged, I find it less important.
Closes #772
I'm unsure about the xml writer implementation, but I've added a hack for now